Problem with DXL Layout in batch mode

We use Analysis Wizard to create a DXL Layout Column with object identifiers from in-links and out-links objects.
Some of our formal modules include this column in its default view, which leads to a problem in batch mode.

Every time a DXL script tries to open one of these modules (i.e. a View with the DXL layout I mentioned before), I get the following error message.

+
-E- DXL: <layout/actual/suspect_out.inc:30> incorrect arguments for (==)
Included from:
<layout/suspect_Out_all.dxl:13>
<Line:15>
-E- DXL: <layout/actual/suspect_out.inc:30> undeclared variable (g_bSuspectLinkUtilityOn)
Included from:
<layout/suspect_Out_all.dxl:13>
<Line:15>
-E- DXL: <layout/actual/suspect_out.inc:37> incorrectly concatenated tokens
Included from:
<layout/suspect_Out_all.dxl:13>
<Line:15>
-E- DXL: <layout/actual/suspect_out.inc:37> undeclared variable (g_skpSuspectOutLinkModulesOpened)
Included from:
<layout/suspect_Out_all.dxl:13>
<Line:15>
-E- DXL: <layout/actual/suspect_out.inc:37> undeclared variable (fnOpenAllOutLinkedModules)
Included from:
<layout/suspect_Out_all.dxl:13>
<Line:15>
-E- DXL: <layout/actual/suspect_out.inc:41> incorrect arguments for (>)
Included from:
<layout/suspect_Out_all.dxl:13>
<Line:15>
-E- DXL: <layout/actual/suspect_out.inc:41> undeclared variable (fnDetermineSuspectOutLinks)
Included from:
<layout/suspect_Out_all.dxl:13>
<Line:15>
-E- DXL: <layout/actual/suspect_out.inc:41> incorrectly concatenated tokens
Included from:
<layout/suspect_Out_all.dxl:13>
<Line:15>
-E- DXL: <layout/actual/suspect_out.inc:60> incorrectly concatenated tokens
Included from:
<layout/suspect_Out_all.dxl:13>
<Line:15>
-E- DXL: <layout/actual/suspect_out.inc:60> undeclared variable (S_ATTR_SUSPICION_CLEARED_FORWARDS)
Included from:
<layout/suspect_Out_all.dxl:13>
<Line:15>
too many messages -- suspending error reporting-I- DXL: all done with 23 errors and 0 warnings
DXL contains 23 errors
+

If I run the same script in interactive mode, everything works perfectly.

It makes me think that I should use some "#include" on DXL standard library to declare all those missing variables like "g_bSuspectLinkUtilityOn", "g_skpSuspectOutLinkModulesOpened", etc., but I can't figure out which one it is.

Does anyone know how to solve this problems?
BraulioH - Mon Feb 08 09:22:52 EST 2010

Re: Problem with DXL Layout in batch mode
Mathias Mamsch - Mon Feb 08 12:58:35 EST 2010

Re: Problem with DXL Layout in batch mode
llandale - Tue Feb 09 15:57:43 EST 2010

Batch mode doesn't load all the same #includes as does the normal mode.

If you find and issue the correct #include file, then you will get double-defined errors in the Layout in normal mode.

Routinely open your modules:

Module mod = read(NameModFull, false, true)

The first bool 'false' means invisible; the second bool 'true' means load the standard view (ignoring default views). Thus, your layouts won't run and it doesn't matter if they would fail in Batch mode.

• Louie